Other References

The beneficiary's (internal) transaction identifier (transactionReference) accompanies the message throughout its lifecycle. This data is generated by the beneficiary or the endpoint made available to the beneficiary. The purpose of the identifier is to allow the beneficiary to track the processing of their mandate in every message, as the data also appears on the account statement and in the status information message. The beneficiary's identifier does not go into the end-to-end ID field in the interbank space, because the GIRO standard application requires the payer's bank to fill it in a specified way. The beneficiary's internal transaction identifier shares a field (credTranId) in the EAM with the Aggregator's unique identifier, so the beneficiary's bank also receives the two identifiers concatenated in the interbank transfer message (or in the EAM code). The Aggregator's unique operation identifier (paymentReference) also accompanies the EAM throughout its lifecycle. The Aggregator provides this identifier in the response to the EAM request, in the URL code. The paymentReference identifier must be used for status queries and also during EAM cancellation. The Aggregator's unique identifier is concatenated with the beneficiary's (internal) transaction identifier in the URL, and the beneficiary's bank receives the two identifiers in a single field (credTranId) separated by an underscore and provides them to its customer. It is worth noting that the Aggregator also assigns such an identifier (for statistical purposes) to createPayment initiations that are rejected with general business validation errors.